home *** CD-ROM | disk | FTP | other *** search
-
-
-
- yyyyppppsssseeeetttt((((1111MMMM)))) yyyyppppsssseeeetttt((((1111MMMM))))
-
-
-
- NNNNAAAAMMMMEEEE
- ypset - point ypbind at a particular NIS server
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- yyyyppppsssseeeetttt [ ----VVVV1111|----VVVV2222 ] [ ----hhhh _h_o_s_t ] [ ----dddd _d_o_m_a_i_n ] _s_e_r_v_e_r
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- _y_p_s_e_t tells _y_p_b_i_n_d(1M) to get the network information service (NIS) for
- the specified _d_o_m_a_i_n from the _y_p_s_e_r_v process running on _s_e_r_v_e_r. If
- _s_e_r_v_e_r is down, or isn't running _y_p_s_e_r_v, this is not discovered until an
- NIS client process tries to get a binding for the domain. At this point,
- the binding set by _y_p_s_e_t will be tested by _y_p_b_i_n_d. If the binding is
- invalid, _y_p_b_i_n_d attempts to rebind for the same domain.
-
- By default, _y_p_b_i_n_d does not allow _y_p_s_e_t operations from local or remote
- hosts. _y_p_s_e_t returns the error message
-
- ypset: Sorry, I couldn't send my RPC message to ypbind on host _n_i_s_s_e_r_v_e_r
-
- when _y_p_b_i_n_d rejects the attempt.
-
- _y_p_s_e_t is useful for binding a client node that is not on a broadcast net
- or is on a broadcast net that isn't running an NIS server host. It also
- is useful for debugging NIS client applications, for instance where an
- NIS map only exists at a single NIS server host.
-
- In cases where several hosts on the local net are supplying NIS services,
- it is possible for _y_p_b_i_n_d to rebind to another host even while you
- attempt to find out if the _y_p_s_e_t operation succeeded. That is, you can
- type _yyyy_pppp_ssss_eeee_tttt _hhhh_oooo_ssss_tttt_1111_;;;; _yyyy_pppp_wwww_hhhh_iiii_cccc_hhhh and get the response _h_o_s_t_2, which can be
- confusing. This is a function of the NIS subsystem's attempt to load-
- balance among the available NIS servers It occurs when _h_o_s_t_1 does not
- respond to _y_p_b_i_n_d because it is not running _y_p_s_e_r_v (or is overloaded) and
- _h_o_s_t_2, running _y_p_s_e_r_v, gets the binding.
-
- _s_e_r_v_e_r indicates the NIS server to bind to and can be specified as a name
- or an IP address. If specified as a name, _y_p_s_e_t attempt to use NIS
- services to resolve the name to an IP address. This works only if the
- node has a current valid binding for the domain in question. In most
- cases, _s_e_r_v_e_r should be specified as an IP address.
-
- Refer to _y_p_f_i_l_e_s(4) and _y_p_s_e_r_v(1M) for an overview of NIS.
-
- OOOOPPPPTTTTIIIIOOOONNNNSSSS
- ----VVVV1111 Bind _s_e_r_v_e_r for the (old) v.1 NIS protocol.
-
- ----VVVV2222 Bind _s_e_r_v_e_r for the (current) v.2 NIS protocol.
-
- If no version is supplied, _y_p_s_e_t, first attempts to set the
- domain for the (current) v.2 protocol. If this attempt
- fails, _y_p_s_e_t, attempts to set the domain for the (old) v.1
- protocol.
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- yyyyppppsssseeeetttt((((1111MMMM)))) yyyyppppsssseeeetttt((((1111MMMM))))
-
-
-
- ----hhhh _h_o_s_t Set _y_p_b_i_n_d's binding on _h_o_s_t, instead of locally. _h_o_s_t can
- be specified as a name or as an Internet address.
-
- ----dddd _d_o_m_a_i_n Use _d_o_m_a_i_n instead of the default domain.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- ypserv(1M), ypwhich(1), ypfiles(4).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-